Systems and methods for dynamic management of stored cache data based on predictive usage information

ABSTRACT

Embodiments of the invention are directed to systems, methods and computer program products structured for dynamic management of stored cache data based on predictive usage information. The invention is structured for proactive alleviation of obsolete data, dynamic pre-population and fetching of cached data based on determining actions preceding initiation of activities. Specifically, the invention is configured to detect, via a proactive processor application, a first access event via a first network device associated with a first communication channel at a first time interval, such that the first access event is detected prior to initiation of a first technology activity event by the user. The invention is also structured to populate the first adapted hierarchical cache data object for use at a technology application associated with the first network device prior to the initiation of the first technology activity event by the user.

FIELD OF THE INVENTION

The present invention generally relates to dynamic and adaptedmanagement of stored cache data based on predictive usage information.Embodiments of the invention are structured for light-weight granulardata caching based on construction of adapted hierarchical data objectswith improved indexing, as well as dynamic pre-population and fetchingof cached data based on determining actions preceding initiation ofactivities.

BACKGROUND

There has been a significant increase in the number of electronicactivities, particularly online and mobile activities due to widespreaduse of smartphone, tablet computers, laptop computers, transactionterminals, and electronic computing devices in general. Performingelectronic activities requires the devices to repeatedly fetch relevantdata from backend servers, external databases/networks, and/or otherbackend systems/devices. However, fetching data from backend systemsresults in a time lag, causing delays in execution of the electronicactivities. Some conventional systems employ data caching, in an attemptto reduce these delays. However, these conventional systems typicallycache almost all provided data commencing since the time of the users'login, in its entirety. Conventional systems are neither able todetermine the relevancy of the data for current activities, much lessfor future activities, nor envisage how long the data needs to be cachedfor, thereby resulting in large amounts of irrelevant cached data thatis stored over extended time periods. However, caching such immenseamounts of data causes severe burdens on data caching servers, such asheavy memory and processing loads. Moreover, the enormity of the amountsof the data being cached results in slow turnaround times for thesearching and fetching relevant data, thereby impeding the very purposeof data caching. In addition, typically, the data cached by conventionalsystems is specific to a particular device, and conventional systems arenot able to transform cached data across channels, causing furtherdelays.

The present invention provides a novel dynamic management of storedcache data, that alleviates the above deficiencies and also providesother advantages. The previous discussion of the background to theinvention is provided for illustrative purposes only and is not anacknowledgement or admission that any of the material referred to is orwas part of the common general knowledge as at the priority date of theapplication.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

Embodiments of the present invention address these and/or other needs byproviding systems, computer program products and methods for dynamicmanagement of stored cache data based on usage information. Typically,the system is structured for light-weight granular data caching based onconstruction of adapted hierarchical data objects with improvedindexing, for reducing memory and processing burdens on data cachingservers and reducing turnaround time for activity execution. In someinstances, the system comprises: at least one memory device withcomputer-readable program code stored thereon, at least onecommunication device, at least one processing device operatively coupledto the at least one memory device and the at least one communicationdevice, wherein executing the computer-readable program code istypically configured to cause the at least one processing device toperform, execute or implement one or more features or steps of theinvention such as: initiate, via a proactive processor application, atechnology usage analysis mechanism comprising technology usage dataassociated with a plurality of users; construct, via the proactiveprocessor application, an adapted truncated cache data retrieval commandsuch that the truncated cache data retrieval command is structured toselectively retrieve data that matches the technology usage data;trigger, via the proactive processor, retrieval of truncated technologydata for caching from a usage database based on the adapted truncatedcache data retrieval command; construct a plurality of adaptedhierarchical cache data objects, for each of the plurality of users, ina distributed cache layer, comprising: identifying a plurality of dataelement types in the retrieved truncated technology data based onparsing the retrieved truncated technology data; splitting the retrievedtruncated technology data into a plurality of cache data objects suchthat each of the plurality of cache data objects comprises an associateddata element type; determining a hierarchy of each of the plurality ofcache data objects; and transforming the plurality of cache data objectsinto the plurality of adapted hierarchical cache data objects based onthe determined hierarchy, wherein each of the adapted hierarchical cachedata objects are (i) mapped to an associated cache data objectidentifier, and (ii) linked to a parent user identifier data element;and cache the constructed plurality of adapted hierarchical cache dataobjects, for each of the plurality of users, in the distributed cachelayer.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: detect, via a proactiveprocessor application, a first access event via a first network deviceassociated with a first communication channel at a first time interval,such that the first access event is detected prior to initiation of afirst technology activity event by the user; and populate a firstadapted hierarchical cache data object of the constructed plurality ofadapted hierarchical cache data objects for use at a technologyapplication associated with the first network device prior to theinitiation of the first technology activity event by the user.

In some embodiments, or in combination with any of the previousembodiments, initiating the technology usage analysis mechanism furthercomprises: retrieving, via a usage monitor engine application, metadataassociated with prior technology usage events associated with theplurality of users, wherein the prior technology usage events comprise auser activity log associated with activities initiated by the pluralityof users using one or more network devices associated with one or morecommunication channels.

In some embodiments, or in combination with any of the previousembodiments, constructing the adapted truncated cache data retrievalcommand further comprises: analyzing the metadata associated with theprior technology usage events associated with the plurality of users;constructing, for each of the plurality of users, at least one useraccess routine based on determining one or more usage patterns in themetadata associated with the prior technology usage events, whereindetermining one or more usage patterns further comprises determining amatch between metadata associated with a first prior technology usageevent at a first time interval, and metadata associated with a priorsecond technology usage event at a second time interval succeeding thefirst time interval, wherein the at least one user access routinecomprises one or more user activity events based on the one user accessroutine; determining, for each of the plurality of users, (i) one ormore event attributes associated with each of the one or more useractivity events in the associated at least one user access routine, and(ii) compatible cache data objects associated with the one or more eventattributes; and constructing, for each of the plurality of users, theadapted truncated cache data retrieval command to retrieve thecompatible cache data objects associated with the one or more eventattributes associated with the at least one user access routine.

In some embodiments, or in combination with any of the previousembodiments, determining one or more usage patterns further comprises:determining a match between metadata associated with a first sequence ofprior technology usage events at a third time interval, and metadataassociated with a second sequence of prior technology usages event at afourth time interval succeeding the third time interval.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: construct one or moreadditional child cache data objects; and append the plurality of adaptedhierarchical cache data objects with the one or more additional childcache data objects.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: for each of the pluralityof adapted hierarchical cache data objects of each of the plurality ofusers, determine an associated determine a time to live parameter; andlink the determined time to live parameter to the associated adaptedhierarchical cache data object such that the adapted hierarchical cachedata object is (i) stored only for a first time interval associated withthe duration of the time to live parameter, and (ii) dynamicallyexpunged upon elapse of the first time interval associated with the timeto live parameter.

In some embodiments, or in combination with any of the previousembodiments, the plurality of adapted hierarchical cache data objectsassociated with a first user comprise a first adapted hierarchical cachedata object and a second adapted hierarchical cache data object of theplurality of adapted hierarchical cache data objects. Here, determiningthe associated time to live parameter further comprises: determining afirst time to live parameter associated with the first adaptedhierarchical cache data object of the first user; and determining asecond time to live parameter associated with the second adaptedhierarchical cache data object of the first user; and wherein the firsttime to live parameter exceeds the second time to live parameter suchthat the second adapted hierarchical cache data object is dynamicallyexpunged prior to the dynamic expunging of the first adaptedhierarchical cache data object.

In some embodiments, or in combination with any of the previousembodiments, the plurality of adapted hierarchical cache data objectscomprise a first adapted hierarchical cache data object associated witha first user, and a second adapted hierarchical cache data objectassociated with a second user, wherein the first adapted hierarchicalcache data object matches the second adapted hierarchical cache dataobject. Here, determining the associated time to live parameter furthercomprises: determining a first time to live parameter associated withthe first adapted hierarchical cache data object of the first user; anddetermining a second time to live parameter associated with the secondadapted hierarchical cache data object of the second user; and whereinthe first time to live parameter exceeds the second time to liveparameter such that the second adapted hierarchical cache data object isdynamically expunged prior to the dynamic expunging of the first adaptedhierarchical cache data object.

In some embodiments, or in combination with any of the previousembodiments, determining the associated time to live parameter furthercomprises: for a first adapted hierarchical cache data object of theplurality of adapted hierarchical cache data objects of a first user ofthe plurality of users, determining an associated first storage levellocation and a second storage level location; and determining a firsttime to live parameter associated with the first storage level location,and determining a second time to live parameter associated with thesecond storage level location, wherein the first time to live parameterexceeds the second time to live parameter such that the first adaptedhierarchical cache data object at the second storage level location isdynamically expunged prior to the dynamic expunging of the first adaptedhierarchical cache data object at the first storage level location.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: determine an update to asystem of records database system; and expunge the plurality of adaptedhierarchical cache data objects in real-time, in response to determiningthe update to a system of records database system.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: for each of the pluralityof adapted hierarchical cache data objects of each of the plurality ofusers, determine an associated determine a time to fetch parameter; andlink the determined time to fetch parameter to the associated adaptedhierarchical cache data object.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: for each of the pluralityof adapted hierarchical cache data objects of each of the plurality ofusers, dynamically update the adapted hierarchical cache data object ata time interval preceding the associated determined time to fetchparameter.

Embodiments of the present invention address these and/or other needs byproviding systems, computer program products and methods for dynamicmanagement of stored cache data based on predictive usage information.Typically, the system is structured for proactive alleviation ofobsolete data, dynamic pre-population and fetching of cached data basedon determining actions preceding initiation of activities, forpreventing data redundancy based errors, and reducing memory andprocessing burdens on data caching servers and reducing turnaround timefor activity execution. In some instances, the system comprises: atleast one memory device with computer-readable program code storedthereon, at least one communication device, at least one processingdevice operatively coupled to the at least one memory device and the atleast one communication device, wherein executing the computer-readableprogram code is typically configured to cause the at least oneprocessing device to perform, execute or implement one or more featuresor steps of the invention such as: detect, via a proactive processorapplication, a first access event via a first network device associatedwith a first communication channel at a first time interval, such thatthe first access event is detected prior to initiation of a firsttechnology activity event by the user; determine a proactive technologyactivity event associated with the user that is (i) compatible with thefirst network device associated with a first communication channel and(ii) matches the first access event; determine a first adaptedhierarchical cache data object of the plurality of adapted hierarchicalcache data objects associated with the first user that is compatiblewith the proactive technology activity event; trigger one or more datapresence checks associated with the first adapted hierarchical cachedata object at one or more technology network layers; in response to asuccessful data presence check, selectively retrieve truncated cachedata that matches the proactive technology activity event; populate thefirst adapted hierarchical cache data object for use at a technologyapplication associated with the first network device prior to theinitiation of the first technology activity event by the user; detectinitiation of the first technology activity event by a user at a secondtime interval via the first network device associated with the firstcommunication channel; and in response to determining that the firsttechnology activity event matches the proactive technology activityevent, initiate the first technology activity event using the firstadapted hierarchical cache data object.

In some embodiments, or in combination with any of the previousembodiments, determining proactive technology activity event associatedwith the user further comprises: determine access attributes associatedwith the first access event; retrieve, via a usage monitor engineapplication, metadata associated with prior technology usage eventsassociated with the users; determine a first user access routine basedon determining one or more usage patterns in the metadata associatedwith the prior technology usage events that match the access attributesassociated with the first access event; and determine a proactivetechnology activity event associated with the user that is (i)compatible with the first network device associated with a firstcommunication channel and (ii) matches the first user access routine.

In some embodiments, or in combination with any of the previousembodiments, determining the first adapted hierarchical cache dataobject of the plurality of adapted hierarchical cache data objectsfurther comprises: determine one or more event attributes associatedwith the proactive technology activity event; and determine the firstadapted hierarchical cache data object of the plurality of adaptedhierarchical cache data objects associated with the first user that iscompatible with the one or more event attributes of the proactivetechnology activity event.

In some embodiments, or in combination with any of the previousembodiments, selectively retrieving truncated cache data comprisesretrieving truncated cache data that matches one or more eventattributes of the proactive technology activity event, furthercomprising: retrieving the first adapted hierarchical cache data objectof the plurality of adapted hierarchical cache data objects associatedwith the first user that is compatible with the one or more eventattributes of the proactive technology activity event.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: trigger a first datapresence check associated with the first adapted hierarchical cache dataobject at an application layer associated with the first communicationchannel.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: in response to a successfulfirst data presence check, selectively retrieve truncated cache datathat matches the one or more event attributes of the proactivetechnology activity event, comprising selectively retrieving the firstadapted hierarchical cache data object of the plurality of adaptedhierarchical cache data objects associated with the first user that iscompatible with the one or more event attributes of the proactivetechnology activity event at a second time interval prior to initiationof the first technology activity event by the user.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: in response to anunsuccessful first data presence check, trigger a second data presencecheck associated with the first adapted hierarchical cache data objectat an entity layer associated with the first communication channel.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: in response to a successfulsecond data presence check, selectively retrieve truncated cache datathat matches the one or more event attributes of the proactivetechnology activity event, comprising: retrieving the first adaptedhierarchical cache data object of the plurality of adapted hierarchicalcache data objects associated with the first user that is compatiblewith the one or more event attributes of the proactive technologyactivity event prior to initiation of the first technology activityevent by the user; and transmitting retrieved the first adaptedhierarchical cache data object from the entity layer to the applicationlayer prior to initiation of the first technology activity event by theuser.

In some embodiments, or in combination with any of the previousembodiments, selectively retrieving truncated cache data, furthercomprises: accessing the plurality of adapted hierarchical cache dataobjects associated with a plurality of users; and indexing the pluralityof adapted hierarchical cache data objects associated with a pluralityof users based on a parent user identifier data element associated withthe first user.

In some embodiments, or in combination with any of the previousembodiments, populate the first adapted hierarchical cache data objectfor use at a technology application associated with the first networkdevice prior to the initiation of the first technology activity event bythe user, further comprises: determine a time latency associated withthe proactive technology activity event, wherein determining the timelatency comprises determining a time to fetch parameter associated withthe first adapted hierarchical cache data object; proactively extract,via a data caching application, the first adapted hierarchical cachedata object at a predetermined first time interval preceding a secondtime associated with initiation of the second technology activity event,wherein the predetermined first time interval is associated with thedetermined time to fetch parameter associated with the time latency ofthe first technology activity event.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: determine an update to asystem of records database system; and expunge the plurality of adaptedhierarchical cache data objects in real-time, in response to determiningthe update to a system of records database system.

In some embodiments, or in combination with any of the previousembodiments, the invention is structured to: for each of the pluralityof adapted hierarchical cache data objects of each of the plurality ofusers, dynamically update the adapted hierarchical cache data object ata time interval preceding the associated determined time to fetchparameter.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 depicts a network environment 100 for dynamic management ofstored cache data, in accordance with one embodiment of the presentinvention;

FIG. 2A depicts a schematic representation 200A of a network layerenvironment for dynamic management of stored cache data, in accordancewith one embodiment of the present invention;

FIG. 2B depicts a schematic representation 200B of a network processingenvironment for dynamic management of stored cache data, in accordancewith one embodiment of the present invention;

FIG. 3A depicts a high level process flow 300A for dynamic management ofstored cache data by construction of adapted hierarchical cache dataobjects, in accordance with one embodiment of the present invention;

FIG. 3B depicts a schematic representation 300B of cached data;

FIG. 3C depicts a schematic representation 3000 of adapted hierarchicalcache data objects, in accordance with one embodiment of the presentinvention; and

FIG. 4 depicts a high level process flow 400 for dynamic management ofstored cache data by pre-population of cache data based on predictiveusage information, in accordance with one embodiment of the presentinvention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to elements throughout. Wherepossible, any terms expressed in the singular form herein are meant toalso include the plural form and vice versa, unless explicitly statedotherwise. Also, as used herein, the term “a” and/or “an” shall mean“one or more,” even though the phrase “one or more” is also used herein.Furthermore, when it is said herein that something is “based on”something else, it may be based on one or more other things as well. Inother words, unless expressly indicated otherwise, as used herein “basedon” means “based at least in part on” or “based at least partially on.”

In some embodiments, an “entity” or “enterprise” as used herein may beany institution or establishment, associated with a network connectedresource transfer platform, and particularly geolocation systems anddevices. As such, the entity may be any institution, group, association,financial institution, merchant, establishment, company, union,authority or the like.

As described herein, a “user” is an individual associated with anentity. As such, in some embodiments, the user may be an individualhaving past relationships, current relationships or potential futurerelationships with an entity. In some embodiments, a “user” may be anemployee (e.g., an associate, a project manager, an IT specialist, amanager, an administrator, an internal operations analyst, or the like)of the entity or enterprises affiliated with the entity, capable ofoperating the systems described herein. In some embodiments, a “user”may be any individual, entity or system who has a relationship with theentity, such as a customer or a prospective customer. In otherembodiments, a user may be a system performing one or more tasksdescribed herein.

In the instances where the entity is a resource entity or a merchant,financial institution and the like, a user may be an individual orentity with one or more relationships, affiliations or accounts with theentity (for example, the merchant, the financial institution). In someembodiments, the user may be an entity or financial institution employee(e.g., an underwriter, a project manager, an IT specialist, a manager,an administrator, an internal operations analyst, bank teller or thelike) capable of operating the system described herein. In someembodiments, a user may be any individual or entity who has arelationship with a customer of the entity or financial institution. Forpurposes of this invention, the term “user” and “customer” may be usedinterchangeably. A “technology resource” or “account” may be therelationship that the user has with the entity. Examples of technologyresources include a deposit account, such as a transactional account(e.g. a banking account), a savings account, an investment account, amoney market account, a time deposit, a demand deposit, a pre-paidaccount, a credit account, user information, or the like. The technologyresource or account is typically associated with and/or maintained by anentity, and is typically associated with technology infrastructure suchthat the resource or account may be accessed, modified or acted upon bythe user electronically, for example using or transaction terminals,user devices, merchant systems, and the like. In some embodiments, theentity may provide one or more technology instruments or financialinstruments to the user for executing resource transfer activities orfinancial transactions. In some embodiments, the technologyinstruments/financial instruments like electronic tokens, credit cards,debit cards, checks, loyalty cards, entity user device applications,account identifiers, routing numbers, passcodes and the like areassociated with one or more resources or accounts of the user. In someembodiments, an entity may be any institution, group, association, club,establishment, company, union, authority or the like with which a usermay have a relationship. As discussed, in some embodiments, the entityrepresents a vendor or a merchant with whom the user engages infinancial (for example, resource transfers like purchases, payments,returns, enrolling in merchant accounts and the like) or non-financialtransactions (for resource transfers associated with loyalty programsand the like), either online or in physical stores.

As used herein, a “user interface” may be a graphical user interfacethat facilitates communication using one or more communication mediumssuch as tactile communication (such, as communication via a touchscreen, keyboard, and the like), audio communication, textualcommunication and/or video communication (such as, gestures). Typically,a graphical user interface (GUI) of the present invention is a type ofinterface that allows users to interact with electronic elements/devicessuch as graphical icons and visual indicators such as secondarynotation, as opposed to using only text via the command line. That said,the graphical user interfaces are typically configured for audio, visualand/or textual communication, and are configured to receive input and/orprovide output using one or more user device components and/or externalauxiliary/peripheral devices such as a display, a speaker, a microphone,a touch screen, a camera, a GPS device, a keypad, a mouse, and/or thelike. In some embodiments, the graphical user interface may include bothgraphical elements and text elements. The graphical user interface isconfigured to be presented on one or more display devices associatedwith user devices, entity systems, auxiliary user devices, processingsystems and the like.

An electronic activity, also referred to as a “technology activity”,“technology activity event”, or a “user activity”, such as a “resourcetransfer” or “transaction”, may refer to any activities or communicationbetween a user or entity and the financial institution, between the userand the entity, activities or communication between multiple entities,communication between technology applications and the like. A resourcetransfer may refer to a payment, processing of funds, purchase of goodsor services, a return of goods or services, a payment transaction, acredit transaction, or other interactions involving a user's resource oraccount. In the context of a financial institution or a resource entitysuch as a merchant, a resource transfer may refer to one or more of:transfer of resources/funds between financial accounts (also referred toas “resources”), deposit of resources/funds into a financial account orresource (for example, depositing a check), withdrawal of resources orfinds from a financial account, a sale of goods and/or services,initiating an automated teller machine (ATM) or online banking session,an account balance inquiry, a rewards transfer, opening a bankapplication on a user's computer or mobile device, a user accessingtheir e-wallet, applying one or more coupons to purchases, or any otherinteraction involving the user and/or the user's device that invokes orthat is detectable by or associated with the financial institution. Aresource transfer may also include one or more of the following:renting, selling, and/or leasing goods and/or services (e.g., groceries,stamps, tickets, DVDs, vending machine items, and the like); makingpayments (e.g., paying monthly bills; and the like); loading money ontostored value cards (SVCs) and/or prepaid cards; donating to charities;and/or the like. Unless specifically limited by the context, a “resourcetransfer,” a “transaction,” a “transaction event,” or a “point oftransaction event,” refers to any user activity (financial ornon-financial activity) initiated between a user and a resource entity(such as a merchant), between the user and the financial instruction, orany combination thereof. In some embodiments, a resource transfer ortransaction may refer to financial transactions involving direct orindirect movement of funds through traditional paper transactionprocessing systems (i.e. paper check processing) or through electronictransaction processing systems. In this regard, resource transfers ortransactions may refer to the user initiating a funds/resource transferbetween account, funds/resource transfer as a payment for the purchasefor a product, service, or the like from a merchant, and the like.Typical financial transactions or resource transfers include point ofsale (POS) transactions, automated teller machine (ATM) transactions,person-to-person (P2P) transfers, internet transactions, onlineshopping, electronic funds transfers between accounts, transactions witha financial institution teller, personal checks, conducting purchasesusing loyalty/rewards points etc. When discussing that resourcetransfers or transactions are evaluated it could mean that thetransaction has already occurred, is in the process of occurring orbeing processed, or it has yet to be processed/posted by one or morefinancial institutions. In some embodiments, a resource transfer ortransaction may refer to non-financial activities of the user. In thisregard, the transaction may be a customer account event, such as but notlimited to the customer changing a password, ordering new checks, addingnew accounts, opening new accounts, adding or modifying accountparameters/restrictions, modifying a payee list associated with one ormore accounts, setting up automatic payments, performing/modifyingauthentication procedures, and the like.

In accordance with embodiments of the invention, the term “user” mayrefer to a customer or the like, who utilizes an external apparatus suchas a user device, for executing resource transfers or transactions. Theexternal apparatus may be a user device (computing devices, mobiledevices, smartphones, wearable devices, auxiliary devices, and thelike), a payment instrument (credit cards, debit cards, checks, digitalwallets, currency, loyalty points), and/or payment credentials (accountnumbers, payment instrument identifiers). In some embodiments, the usermay seek to perform one or more user activities using a user applicationof the invention, which is stored on a user device (e.g., as amulti-channel cognitive resource user application mobile application ofthe user's smart phone). In some embodiments, the user may performtransactions by swiping payment instruments at a transaction terminal,for example, by swiping a magnetic strip of a credit card along amagnetic reader of a transaction terminal. In some embodiments, thetransactions may be performed by wireless communication or “tapping”between the customer device and a transaction terminal. In accordancewith some embodiments of the invention, the term “tap” or “tapping” mayrefer to bringing an external apparatus close to or within apredetermined proximity of the activity interface device or transactionterminal interface, or auxiliary user devices, so that information (suchas encrypted tokens, financial resource/account identifiers, and thelike) can be communicated wirelessly between the external apparatus andthe devices using short range wireless transmission technology, suchnear-field communication (NFC) technology, radio-frequency (RF)technology, audio-frequency communication, or the like. Tapping mayinclude physically tapping the user device against an appropriateportion of the auxiliary user device or the transaction terminal or itmay include only waving or holding the user device near an appropriateportion of the auxiliary user device or the transaction terminal withoutmaking physical contact with the transaction terminal.

There has been a significant increase in the number of electronicactivities, particularly online and mobile activities due to widespreaduse of smartphone, tablet computers, laptop computers, transactionterminals, and electronic computing devices in general. Performingelectronic activities requires the devices to repeatedly fetch relevantdata from backend servers, external databases/networks, and/or otherbackend systems/devices. However, fetching data from backend systemsresults in a time lag, causing delays in execution of the electronicactivities. Some conventional systems employ data caching, in an attemptto reduce these delays. However, these conventional systems typicallycache almost all provided data commencing since the time of the users'login, in its entirety. Conventional systems are neither able todetermine the relevancy of the data for current activities, much lessfor future activities, nor envisage how long the data needs to be cachedfor, thereby resulting in large amounts of irrelevant cached data thatis stored over extended time periods. However, caching such immenseamounts of data causes severe burdens on data caching servers, such asheavy memory and processing loads. Moreover, the enormity of the amountsof the data being cached results in slow turnaround times for thesearching and fetching relevant data, thereby impeding the very purposeof data caching. In addition, typically, the data cached by conventionalsystems is specific to a particular device, and conventional systems arenot able to transform cached data across channels, causing furtherdelays.

The present invention, as described in detail with respect to FIGS. 1 to4 , provides a novel dynamic management of stored cache data.Specifically, the present invention is not only structured for selectiveproactive data caching based on light-weight granular data caching basedon construction of adapted hierarchical data objects, for reducingmemory and processing burdens on data caching servers and reducingturnaround time for activity execution, it is also structured forproactive alleviation of obsolete data, dynamic pre-population andfetching of cached data based on determining actions precedinginitiation of activities by caching most current data at precise time tofetch parameters and retaining the data only until precise time to liveparameters and discarding the data thereafter, as well, therebyprecluding perpetual caching of data over extended time periods and alsoprecluding prematurely caching data that is not current. Theimprovements provided by the specific network and application structureof the present invention (involving proactive processors at edge nodes,usage monitor engine, distributed cache storage for storing and indexinghierarchical granular adapted cache data objects, and/or the like) mayresult in immensely faster cache data operations, such as within a fewmilliseconds (e.g., 0.002 seconds), which would otherwise requiremultiple seconds (e.g., 20 seconds) or even minutes in the absence ofthe present invention. For instance, the present invention may provide athousand-fold improvement in processing time, which would not bepossible without the specific network and application structure of thepresent invention involving proactive processors at edge nodes, usagemonitor engine, distributed cache storage for storing and indexinghierarchical granular adapted cache data objects, and/or the like,across application, presentation, entity and service layers.

FIG. 1 illustrates a network environment 100 for dynamic management ofstored cache data, in accordance with one embodiment of the presentinvention. As illustrated in FIG. 1 , a caching technology system 106,is provided configured for dynamic management of stored cache data,e.g., based on analyzing prior usage information and predictingsubsequent usage information. Specifically, the cross-channel datacaching application 144 of the caching technology system 106 isstructured for (i) light-weight granular data caching based onconstruction of adapted hierarchical data objects with improvedindexing, and (ii) proactive alleviation of obsolete data, dynamicpre-population and fetching of cached data based on determining actionspreceding initiation of activities involving caching most current dataat precise time to fetch parameters and retaining the data only untilprecise time to live parameters and discarding the data thereafter, forpreventing data redundancy based errors, and for reducing memory andprocessing burdens on data caching servers and reducing turnaround timefor activity execution. The caching technology system 106 is operativelycoupled, via a network 101 to one or more user devices 104, auxiliaryuser devices 170, resource processing devices 120, entity system(s) 180(e.g., financial institution systems 180), entity databases 190, andother external systems/third-party servers not illustrated herein. Inthis way, the caching technology system 106 can send information to andreceive information from multiple user devices 104, auxiliary userdevices 170, and/or resource processing devices 120, via network 101.

The network 101 may be a global area network (GAN), such as theInternet, a wide area network (WAN), a local area network (LAN), or anyother type of network or combination of networks. The network 101 mayprovide for wireline, wireless, or a combination wireline and wirelesscommunication between devices on the network 101. The network 101 isconfigured to establish an operative connection between otherwiseincompatible devices, for example establishing a communication channel,automatically and in real time, between the one or more user devices 104and one or more of the auxiliary user devices 170 and/or resourceprocessing devices 120, (for example, based on receiving a user input,or when the user device 104 is within a predetermined proximity orbroadcast range of the auxiliary devices 170 and/or resource processingdevices 120), as illustrated by communication channel 101 a. Therefore,the system, via the network 101 may establish, operative connectionsbetween otherwise incompatible devices, for example by establishing acommunication channel 101 a between the one or more user devices 104 andthe auxiliary user devices 170 and/or resource processing devices 120.In this regard, the network 101 (and particularly the communicationchannels 101 a) may take the form of contactless interfaces, short rangewireless transmission technology, such near-field communication (NFC)technology, near-field low energy communication, audio frequency (AF)waves, wireless personal area network, radio-frequency (RF) technology,and/or other suitable communication channels. Tapping may includephysically tapping the external apparatus, such as the user device 104,against an appropriate portion of the auxiliary user device 170 and/orresource processing devices 120, or it may include only waving orholding the external apparatus near an appropriate portion of theauxiliary user device without making physical contact with the auxiliaryuser device and/or resource processing devices 120.

In some embodiments, the user 102 is an individual that wishes toconduct one or more electronic activities or technology activity eventswith resource entities, for example using the user device 104. As such,in some instances, the user device may have multiple user applications122 stored/installed on the user device 104 and the memory device 116 inparticular. In some embodiments, the user application 122 is used toconduct one or more electronic activities or technology activity eventswith resource entities. In some embodiments the user application 122 mayrefer to a third party application or a user application stored on acloud used to access the caching technology system 106 and/or theauxiliary user device 170 through the network 101, communicate with orreceive and interpret signals from auxiliary user devices 170, and thelike. The user 102 may subsequently navigate through the interface,perform one or more searches or initiate one or more activities orresource transfers using a user interface provided by the userapplication 122 of the user device 104. In some embodiments, the user102 may be routed to a particular destination using the user device 104.In some embodiments, a purchase or a transaction may be made by the user102 using the user device 104. In some embodiments the auxiliary userdevice 170 requests and/or receives additional information from thecaching technology system 106, entity system 180 and/or the user device104 for authenticating the user and/or the user device, determiningappropriate transaction queues, performing the transactions and otherfunctions.

FIG. 1 also illustrates the user device 104. The user device 104, hereinreferring to one or more user devices, wherein each device may generallycomprise a communication device 110, a display device 112, ageo-positioning device 113, a processing device 114, and a memory device116. Typically, the user device 104 is a computing system that allows auser 102 to interact with other systems to initiate or to completeactivities, resource transfers, and transactions for products, and thelike. The processing device 114 is operatively coupled to thecommunication device 110 and the memory device 116. The processingdevice 114 uses the communication device 110 to communicate with thenetwork 101 and other devices on the network 101, such as, but notlimited to the entity system 180, the auxiliary user device 170,resource processing devices 120, and the caching technology system 106.As such, the communication device 110 generally comprises a modem,server, or other device for communicating with other devices on thenetwork 101. In some embodiments the network 101 comprises a network ofdistributed servers. In some embodiments, the processing device 114 maybe further coupled to a display device 112, a geo-positioning device113, and/or a transmitter/receiver device, not indicated in FIG. 1 . Thedisplay device 112 may comprise a screen, a speaker, a vibrating deviceor other devices configured to provide information to the user. In someembodiments, the display device 112 provides a presentation of the userinterface of the user application 122. The geo-positioning device 113may comprise global positioning system (GPS) devices, triangulationdevices, accelerometers, and other devices configured to determine thecurrent geographic location of the user device 104 with respect tosatellites, transmitter/beacon devices, telecommunication towers and thelike. In some embodiments the user device 104 may include authenticationdevices like fingerprint scanners, microphones (e.g., for voicerecognition), visual capture devices (e.g., for facial recognition) andthe like that are configured to receive one or more types ofauthentication credentials from the user.

The user device 104 comprises computer-readable instructions 124 storedin the memory device 116, which in one embodiment includes thecomputer-readable instructions 124 of the user application 122. In thisway, users 102 may authenticate themselves, initiate activities, andinteract with or receive and decode signals from the auxiliary userdevices 170 and/or resource processing devices 120, communicate with thecaching technology system 106, authorize a transaction, and/or completea transaction using the central user interface of the user device 104.As discussed previously, the user device 104 may be, for example, adesktop personal computer, a mobile system, such as a cellular phone,smart phone, personal data assistant (PDA), laptop, wearable device, asmart TV, a smart speaker, a home automation hub, augmented/virtualreality devices, or the like. The computer readable instructions 124such as computer readable/executable code of the user application 122,when executed by the processing device 114 are configured to cause theuser device 104 and/or processing device 114 to perform one or moresteps described in this disclosure, or to cause other systems/devices toperform one or more steps described herein.

The resource processing devices 120 or transaction terminals as usedherein may refer to one or more electronic devices that facilitate usertransactions or activities. In this regard the resource processingdevices 120 can comprise Automated Teller Machines (ATMs), resourceterminals or Point of sale devices (POS), vending machines, checkoutregisters, ticket vending machines, automated retail transactiondevices, banking terminals in a financial institution and othertransaction terminals that involve financial transactions in one form oranother. In some embodiments the resource processing device 120 refersto devices that facilitate execution of non-financial transactions oractivities, for example, check-in terminals for various industries, forexample: hospitality, travel, and the like, information kiosks and othertransaction terminals that do not involve a user performing a financialtransaction via the transaction terminal. In some embodiments theresource processing devices 120 facilitate execution of both financialand non-financial transactions/activities. In some embodiments, resourceprocessing devices 120 may refer to user devices that facilitatefinancial and/or non-financial transactions, such as laptop computers,tablet computers, smartphones, wearable devices, personal digitalassistants (PDAs), and other portable or stationary computing devices.In some embodiments, the resource processing devices 120 may be owned,operated and/or otherwise associated entities and are installed atsuitable locations, such that the user can travel to the location of theresource processing device to execute transactions. In some embodiments,the resource processing device 120 may be owned, operated and/orotherwise associated with an entity, such as a financial institution. Insome embodiments, the resource processing devices 120 may be owned,operated and/or otherwise associated with the user. The embodimentsdescribed herein may refer to the initiation and completion of anelectronic activity, a user activity or a transaction.

As illustrated by FIG. 1 , the resource processing device 120 maycomprise an ATM 120 a, a resource terminal 120 b (e.g., a point of saleterminal 120 b), a user device 120 c (such as one or more user device104 and/or one or more auxiliary user devices 170), vending machinesand/or other devices that are configured to facilitate the useractivity. The user device 120 c may be one of the user devices 104 andmay comprise a mobile communication device, such as a cellulartelecommunications device (i.e., a smart phone or mobile phone), acomputing device such as a laptop computer, a personal digital assistant(PDA), a mobile Internet accessing device, or other mobile deviceincluding, but not limited to portable digital assistants (PDAs),pagers, mobile televisions, laptop computers, cameras, video recorders,audio/video player, radio, GPS devices, any combination of theaforementioned, or the like. The resource processing device 120 mayinclude a communication device, a processing device, a user interface,an authentication device and a memory device having an authenticationapplication/module, a resource datastore and one or more processingapplications stored therein.

In some embodiments, the caching technology system 106 (also referred toas the caching technology system environment 106) comprises a pluralityof networked devices, systems, applications, an electronic communicationgenerating and cross-channel data caching application 144 (whoseprocessing steps and the network and application architecture itconstructs and/or operates on are detailed with respect to FIGS. 2B, 3Aand 4 ) and/or servers associated with technology infrastructure of anentity, in operative communication, as illustrated in FIGS. 2A and 2Bdescribed later on. As further illustrated in FIG. 1 , the cachingtechnology system 106 generally comprises a communication device 136, atleast one processing device 138, and a memory device 140. As usedherein, the term “processing device” generally includes circuitry usedfor implementing the communication and/or logic functions of theparticular system. For example, a processing device may include adigital signal processor device, a microprocessor device, and variousanalog-to-digital converters, digital-to-analog converters, and othersupport circuits and/or combinations of the foregoing. Control andsignal processing functions of the system are allocated between theseprocessing devices according to their respective capabilities. Theprocessing device may include functionality to operate one or moresoftware programs based on computer-readable instructions thereof, whichmay be stored in a memory device.

The processing device 138 is operatively coupled to the communicationdevice 136 and the memory device 140. The processing device 138 uses thecommunication device 136 to communicate with the network 101 and otherdevices on the network 101, such as, but not limited to the entitysystems 180, auxiliary user devices 170, resource processing devices120, and/or the user device 104. The processing device 138 uses thecommunication device 136 to communicate with the network 101 and otherdevices of the entity's technology infrastructure, such as, but notlimited to plurality of networked devices, systems, technologyapplications, cross-channel data caching application 144 and/or serversthat may be located across various geographical locations, e.g., via anentity network (not illustrated). As such, the communication device 136generally comprises a modem, server, wireless transmitters, or otherdevices for communicating with devices on the network 101. The memorydevice 140 typically comprises a non-transitory computer readablestorage medium, comprising computer readable/executableinstructions/code, such as the computer-readable instructions 142, asdescribed below.

As further illustrated in FIG. 1 , the caching technology system 106comprises computer-readable instructions 142 or computer readableprogram code 142 stored in the memory device 140, which in oneembodiment includes the computer-readable instructions 142 of across-channel data caching application 144. The computer readableinstructions 142, when executed by the processing device 138 areconfigured to cause the system 106/processing device 138 to perform oneor more steps described in this disclosure, or to cause othersystems/devices (such as the user device 104, the user application 122,resource processing devices 120, entity system 180, entity database 190,and the like) to perform one or more steps described herein. In someembodiments, the memory device 140 includes a data storage for storingdata related to user transactions and resource entity information, butnot limited to data created and/or used by the cross-channel datacaching application 144. The cross-channel data caching application 144,when operated by the processing device 138 is structured for dynamicmanagement of stored cache data, by (i) light-weight granular datacaching based on construction of adapted hierarchical data objects withimproved indexing, and (ii) proactive alleviation of obsolete data,dynamic pre-population and fetching of cached data based on determiningactions preceding initiation of activities involving caching mostcurrent data at precise time to fetch parameters and retaining the dataonly until precise time to live parameters and discarding the datathereafter, for preventing data redundancy based errors, and forreducing memory and processing burdens on data caching servers andreducing turnaround time for activity execution.

FIG. 1 further illustrates one or more auxiliary user devices 170, incommunication with the network 101. The auxiliary user devices maycomprise peripheral devices such as speakers, microphones, smartspeakers, and the like, display devices, a desktop personal computer, amobile system, such as a cellular phone, smart phone, personal dataassistant (PDA), laptop, wearable device, a smart TV, a smart speaker, ahome automation hub, augmented/virtual reality devices, or the like. Insome embodiments, the structure and/or functioning of the auxiliary userdevices 170 is substantially similar to that of the user device(s) 104,while in other embodiments, the auxiliary user devices 170supplement/enhance the structure and/or functioning of the userdevice(s) 104. In some embodiments, the entity database 190 may compriseuser data. In some embodiments, the entity database 190 may comprise thesystem of record (SOR) event data hub 270 described with respect to FIG.2B later on.

FIG. 2A depicts a schematic diagram 200A of a network layer environmentfor dynamic management of stored cache data, in accordance with oneembodiment of the present invention. FIG. 2B depicts a schematic diagram200B of a network processing environment for dynamic management ofstored cache data, in accordance with one embodiment of the presentinvention. The cross-channel data caching application 144 is structuredfor dynamic management of stored cache data. The cross-channel datacaching application 144 is also structured for (i) light-weight granulardata caching based on construction of adapted hierarchical data objectswith improved indexing, and (ii) proactive alleviation of obsolete data,dynamic pre-population and fetching of cached data based on determiningactions preceding initiation of activities, for preventing dataredundancy based errors, and for reducing memory and processing burdenson data caching servers and reducing turnaround time for activityexecution.

FIG. 2A depicts the communication functions framework and/or applicationarchitecture framework of the systems and devices underlying theinvention network environment of FIG. 1 , in accordance with oneembodiment of the invention. Here, the invention may be structured intoa plurality of layers. In some embodiments, each of the layers may bestructured to communicate and interact with only the layers immediatelyabove and below it, unless the layer does not have layers below orabove. It is understood that the application architecture framework isnon-limiting, and that the invention as illustrated in FIGS. 1, 2B, and3A-3C and 4 , may comprise any suitable application architectureframework not illustrated herein.

In the non-limiting instance of application architecture frameworkillustrated by FIG. 2A, the framework may comprise an application layer201 in operative communication with user devices 104, auxiliary userdevices 170 and/or resource processing devices 120. Specifically, theapplication layer 201, via its components: mobile application component201 a, desktop application component 201 b, interactive voice response(IVR) application component 201 c, and/or the like, may operativelycommunicate directly with respective technology or device applicationsof the user devices 104, auxiliary user devices 170 and/or resourceprocessing devices 120 which implement a component of communicationbetween the client and server. The application layer 201 may bestructured for file sharing, message handling, and database access,through the protocols at the application layer, such as HTTP, FTP,SMB/CIFS, TFTP, and SMTP. In some embodiments, the framework comprisesone or more application gateways 202, such as application getaway 202 a,application gateway 202 b, and/or the like. In some embodiments, the oneor more application gateways 202 may be a load balancer structured toroute traffic based on source IP address and port, to a destination IPaddress and port.

The presentation layer 203 is structured for data formatting and datatranslation into a format specified by the application layer during theencapsulation of outgoing messages while being passed down the protocolstack. The presentation layer typically comprises user interface (UI)components 203 a and UI process components 203 b. In some embodiments,the entity layer 204, also referred to as the business layer or domainlogic layer where application logic and program code resides. The entitylayer 204 is structured to accept user requests from the browser,process them, and determine the routes through which the data will beaccessed. The workflows by which the data and requests travel throughthe back end are encoded in the entity layer. In this regard, the entitylayer 204 comprises an application façade 204 a.

The service layer 205 comprises components associated with variousentity service data types such as entity service data type 1 205 a(e.g., rewards data type), entity service data type 2 205 b (e.g., userinformation data type), and entity service data type 3 205 c (e.g.,bookings data type). In some embodiments, the service layer 205 isstructured for data calls and provides access to the persistent storageof an application. The data storage infrastructure includes a server anda database management system, software to communicate with the databaseitself, applications, and user interfaces to obtain data and parse it.

The present invention is structured to construct, and store adaptedhierarchical cache data objects 340 at an underlying cache layer (e.g.,associated with distributed cache database 260 of FIG. 2B), such thatdata is cached in elemental or smaller discrete fragments that can becontrolled, and operated upon individually.

The present invention is structured to dynamically bring forth relevantconstructed adapted hierarchical cache data objects 340 to front layers(e.g., to application layer 101 or presentation layer 203 or entitylayer 204, from underlying storage at a cache layer (e.g., associatedwith distributed cache database 260 of FIG. 2B), via the service layer205), based on determining usage patterns. In this regard, the systemtriggers light-weight calls to pull adapted hierarchical cache dataobjects 340 to application gateways layer 202 (which typically functionas a first interaction point) proactively, based on determining usagepatterns. Here, the system triggers, proactively, light-weight calls topull the only the relevant or required cache data objects of theplurality of adapted hierarchical cache data objects 340 from the cachelayer to entity layer 204 or application layer 201, upon merelydetecting access by a user (e.g., detecting the user has opened aparticular application, the user is in the process of inputting logincredentials, etc.) by determining the technology activity event that theuser is likely to initiate (e.g., based on determined usage patterns),before the user has even begun initiating the technology event. Also,since only the relevant or required cache data objects of the pluralityof adapted hierarchical cache data objects 340 are fetched, the networkbandwidth usage is minimal and not cluttered, and the activityprocessing time is reduced because the required cached data is alreadyfetched and available before the processing of the activity has evenbegun. On the contrary, in conventional systems, the process of fetchingthe cached data can only be even initiated, after activity has beeninitiated and the processing thereof is well underway, becauseconventional systems can typically determine that cached data is neededonly after the processing of the activity is initiated. Moreover,because conventional systems store cached data in immense files, thealready delayed processing of the activity due to delays in beginningthe process of fetching data is further exacerbated by delayed and slowfetching and transmission of the cached data because the entire cacheddata would need to be fetched in its immense size.

Moreover, the system transmits control signals to the application layer201 to cause the application layer 201 and/or its relevant components(e.g., via relevant proactive processors 214 a-214 c) to performperiodic scans of storage locations or systems where user data oractivity data is stored, such as the entity database 190, record (SOR)event data hub 270, the service layer 205, etc., to check for recentupdates to the data and to determine data that is rendered incompatibleand/or redundant in light of the recent updates, to determine obsoletecached data, and/or the like. Consequently, the system transmits controlsignals to the cache layer (e.g., associated with distributed cachedatabase 260 of FIG. 2B), to cause it to (i) flush incompatible,redundant and obsolete data, and (ii) update relevant cache data objectsaccordingly (e.g., by only constructing new cache data objects for thespecific fragments of updated data). In this regard, specifically, thesystem is structured to map adapted hierarchical cache data objects 340to database storage columns (e.g., that of the entity database 190,record (SOR) event data hub 270, the service layer 205, etc.). Here, thecache layer flushes the incompatible, redundant and obsolete storedthereon by integrating the determined recent updates (and the determinedincompatible, redundant and obsolete data) with the mapping of theadapted hierarchical cache data objects 340 to database storage columns.As an improvement provided by the present invention, the cache layer mayselectively flush only relevant fragments of cached data, i.e., onlyrelevant (to the determined updates) adapted hierarchical cache dataobjects of the plurality of the adapted hierarchical cache data objects340, instead of undesirably flushing all of the cached data, or none ofthe cached data. Conventional systems store cached data in immensefiles, and are not capable of selectively flushing or updating specificfragments of data within the immense stored data. In this manner, thepresent invention keeps the cache layer lighter by removingincompatible, redundant and obsolete data objects and improves indexingon the cache layer.

In this manner, relevant and required cache data can be fetched fasterto the application layer 201 and/or the associated devices (104, 170,120, and/or the like) and time lag for processing activities using thefetched cache data can be eliminated or significantly reduced because(i) the relevant and required cache data objects (of the plurality ofthe adapted hierarchical cache data objects 340) are fetched beforetechnology activity event is even initiated by a user at a device (e.g.,devices 104, 170, 120, and/or the like), and (ii) only light-weight,i.e., minimal data size cache data objects travel through the network,keeping the network response and communication/transmission responsequicker and lighter.

As illustrated in FIG. 2B, the novel network environment comprises aplurality of communication channels represented by mobile application201 a (e.g., associated with a communication channel type A), desktopapplication 201 b (e.g., associated with a communication channel typeB), interactive voice response (IVR) application 201 c (e.g., associatedwith a communication channel type C), and/or the like, e.g., at theapplication layer 201 (as illustrated in FIG. 2A). Here,channel-specific localized cache data stores (212 a, 212 b, 212 c) areprovided at each communication channel as illustrated. Typically, thecache data stores 212 a-212 c are structured for temporarily storingfetched cache data in the format compatible with the respectivecommunication channel, e.g., proactively fetched relevant cache dataobjects, where each individual cache data object is temporarily storeduntil its specific individual time to live parameter.

A plurality of proactive processors (214 a, 214 b, 214 c) are providedfor each respective communication channel as illustrated, and areoperatively coupled to the respective channel-specific localized cachedata stores (212 a, 212 b, 212 c). The proactive processors 214 a-214 care structured for collecting metadata associated with access events(e.g., the user opening a particular application, the user inputtinglogin credentials, etc.) associated with the respective coupled channel(e.g., via communication channels 216 a, 216 b, 216 c), transmit theextracted metadata to a usage monitor engine 220 for analyzing themetadata of the access event to determine a likely technology activityevent to be initiated by the user at the respective channel, andconsequently initiate proactive events to populate relevant and required(for the determined likely activity to be initiated by the user) adaptedhierarchical cache data objects of the plurality of the adaptedhierarchical cache data objects 340 at the respective cache data stores(212 a, 212 b, 212 c).

Here, the plurality of proactive processors (214 a, 214 b, 214 c) areoperatively coupled to the usage monitor engine 220 (also referred to asa usage monitor engine application 220). The usage monitor engine 220 isstructured to analyze event metadata retrieved from the entity layer 204and/or the proactive processors 214 a-214 c, over time todetermine/construct usage patterns for each user, and for each specificchannel that the user utilizes for conducting network activity events.In this regard, the usage monitor engine 220 may receive an event feedtagged against a user specific access from the entity layer 214, asindicated by channel 224. In some embodiments, the usage monitor engine220 is structured to dynamically and consistently modify and update theusage patterns as additional activities are analyzed thereby, andtransmit current usage updates to the entity layer 214 as indicated bychannel 222. The usage monitor engine 220 is further structured toanalyze extracted metadata associated with access events (received froma respective proactive processor (214 a-214 c)), and determine matcheswith the constructed usage patterns of the particular user at thespecific channel, in order to determine a likely technology activityevent to be initiated (e.g., imminently) by the user at the respectivechannel, and transmit the same to the respective proactive processor(214 a-214 c).

As discussed, the usage monitor engine 220 is operatively coupled to theentity layer 204. The usage monitor engine 220 is structured todynamically and consistently modify and update the usage patterns asadditional activities are analyzed thereby, and transmit current usageupdates to the entity layer 214 as indicated by channel 222. Inresponse, the entity layer 204 is structured to determine thepersonalized and adapted relevant data, specific to the particular userand their usage patterns, to be cached for subsequent activities inaccordance with the usage patterns and extract the relevant data to becached. Here, the entity layer 204 may in turn communicate withapplicable the service layer components such as entity service data type1 205 a (e.g., rewards data type), entity service data type 2 205 b(e.g., user information data type), and entity service data type 3 205 c(e.g., bookings data type) to retrieve the relevant data from the systemof record (SOR) event datahub 270. Once the relevant data to be cachedis retrieved, adapted hierarchical cache data objects 340 areconstructed and stored at the distributed cache 260 (as indicated bycommunication channel 272). In other words, the entity layer 204 isstructured to push personalized adapted hierarchical cache data objects340 to the distributed cache storage 260. Here, the adapted hierarchicalcache data objects 340 (340 a, 340 b, 340 c, . . . , 340 n) constructedby the invention are stored at the distributed cache storage 260.

Moreover, the entity layer 204 (automatically or based on receivinginstructions or triggers) may perform periodic scans of storagelocations or systems where user data or activity data is stored, such asthe entity database 190, record (SOR) event data hub 270 (which may be abackend system) for recent updates to the data and to determine datathat is rendered incompatible and/or redundant in light of the recentupdates, to determine obsolete cached data, and/or the like.Consequently, the entity layer 204 (automatically or based on receivinginstructions or triggers) transmits control signals to the cache layer(e.g., associated with distributed cache database 260 of FIG. 2B), tocause it to (i) delete/flush incompatible, redundant and obsolete data,and (ii) update relevant cache data objects accordingly (e.g., by onlyconstructing new cache data objects for the specific fragments ofupdated data).

The entity layer 204 is further operatively coupled to the plurality ofproactive processors (214 a, 214 b, 214 c). After a proactive processor(214 a, 214 b, 214 c) (e.g., via the usage monitor engine 220)determines a technology activity event to be initiated by the user, theproactive processor (214 a, 214 b, 214 c) may trigger the entity layer204 (e.g., via respective communication channels 218 a, 218 b, 218 c) tocheck if the relevant and required (for the determined likely activityto be initiated by the user) adapted hierarchical cache data objects arepresent at the entity layer 204, and in not, fetch the same from thedistributed cache 260 at the cache layer to the entity layer 204 (viacommunication channel 262). The extracted relevant and required (for thedetermined likely activity to be initiated by the user) adaptedhierarchical cache data objects of the plurality of the adaptedhierarchical cache data objects 340 may then be populated at therespective cache data stores (212 a, 212 b, 212 c) via the proactiveprocessors (214 a, 214 b, 214 c).

In some embodiments, as a non-limiting example, during a regularlearning operation mode or an initial set-up mode, once an activity isinitiated by a user at any of the plurality of communication channels,mobile application 201 a, desktop application 201 b, interactive voiceresponse (IVR) application 201 c, and/or the like, the applicationcommunicates with the entity layer 204 to retrieve the data required forthe activity, as indicated by communication channels 215 a, 215 b, and215 c. The entity layer 204 may in turn communicate with applicable theservice layer components such as entity service data type 1 205 a (e.g.,rewards data type), entity service data type 2 205 b (e.g., userinformation data type), and entity service data type 3 205 c (e.g.,bookings data type) to retrieve the relevant data from the system ofrecord (SOR) event datahub 270. As a part of a technology usage analysismechanism, the entity layer 204 may transmit an event feed comprisingtechnology usage data (e.g., metadata associated with the initiatedactivities, activities being processed, completed activities, and/or thelike) tagged against a user specific access to the usage monitor engine220. In some embodiments, the entity layer 204 may cross-tag themetadata with respective activity attributes such as (i) activitychannel attributes (e.g., type of communication channel, associatedtechnology application, etc.), (ii) activity parameters (e.g., activitytype, authentication requirements, activity time interval, activityduration, etc.), (iii) data required for processing of the activity(e.g., cached data fetched, data transmitted, etc.), and/or the like,for each individual user. The usage monitor engine 220 is structured toanalyze event metadata retrieved from the entity layer 204 (and/or theproactive processors 214 a-214 c,) over time to determine/constructusage patterns for each user, and for each specific channel that theuser utilizes for conducting network activity events. The usage monitorengine 220 is structured to analyze event metadata retrieved from theentity layer 204 and/or the proactive processors 214 a-214 c, over timeto determine/construct usage patterns for each user, and for eachspecific channel that the user utilizes for conducting network activityevents.

The system (e.g., at the proactive processors 214 a-214 c) may analyzethe determined usage patterns, and determines the specific technologydata to be cached for likely recurring events and the compatible formatand data transformation required for the respective channel of thepredicted event. The system (e.g., at the proactive processors 214 a-214c) may trigger retrieval of truncated technology data (i.e., only thespecific data portions that are required to be cached) for caching froma usage database (SOR event datahub 270), e.g., via entity layer 204 incommunication with applicable the service layer components such asentity service data type 1 205 a (e.g., rewards data type), entityservice data type 2 205 b (e.g., user information data type), and entityservice data type 3 205 c (e.g., bookings data type). The system maythen construct a plurality of adapted hierarchical cache data objects240 in a distributed cache layer (distributed cache 260 at the cachelayer). Here, as described later on with respect to FIG. 3000 , thesystem may identify a plurality of data element types 344, split theretrieved truncated technology data into a plurality of cache dataobjects 340, determine a hierarchy of each of the plurality of cachedata objects 340, map the cache data object 340 to an associated cachedata object identifier 342, and link (DS1, DS2, . . . , DSN) the cachedata object 340 to a parent user identifier data element. The system maythen cache the constructed plurality of adapted hierarchical cache dataobjects 340 at the distributed cache 260 at the cache layer, forsubsequent use during a proactive operation mode.

In some embodiments, during a proactive operation mode, the usagemonitor engine 220 is structured to analyze event metadata retrievedfrom the entity layer 204 and/or the proactive processors 214 a-214 c,over time to determine/construct usage patterns for each user, and foreach specific channel that the user utilizes for conducting networkactivity events, as described previously. The proactive processors 214a-214 c may then detect an access event (e.g., the user opening aparticular application, the user inputting login credentials, etc.)associated with the respective coupled channel. Here, the proactiveprocessors 214 a-214 c may extract metadata associated with accessevents associated with the respective coupled channel (e.g., viacommunication channels 216 a, 216 b, 216 c), transmit the extractedmetadata to a usage monitor engine 220 for analyzing the metadata of theaccess event to determine a likely technology activity event to beinitiated by the user at the respective channel. The proactive processor(214 a-214 c) may then analyze the predicted likely technology activityevent to be initiated by the user at the respective channel, and furtherdetermine the data required and relevant for its processing. Theproactive processor (214 a-214 c) may further determine that specificcache data objects associated with the required data. Here, theproactive processor (214 a-214 c) triggers, proactively, light-weightcalls to pull the only the relevant or required cache data objects ofthe plurality of adapted hierarchical cache data objects 340 from thecache layer to entity layer 204 or application layer 201, upon merelydetecting access by a user (e.g., detecting the user has opened aparticular application, the user is in the process of inputting logincredentials, etc.) by determining the technology activity event that theuser is likely to initiate (e.g., based on determined usage patterns),before the user has even begun initiating the technology event. Here,the proactive processor (214 a-214 c) may trigger the entity layer 204(e.g., via respective communication channels 218 a, 218 b, 218 c) tocheck if the relevant and required (for the determined likely activityto be initiated by the user) adapted hierarchical cache data objects arepresent at the entity layer 204, and in not, fetch the same from thedistributed cache 260 at the cache layer to the entity layer 204 (viacommunication channel 262). The extracted relevant and required (for thedetermined likely activity to be initiated by the user) adaptedhierarchical cache data objects of the plurality of the adaptedhierarchical cache data objects 340 may then be populated at therespective cache data stores (212 a, 212 b, 212 c) via the proactiveprocessor (214 a-214 c). Subsequently, the proactive processor (214a-214 c) may detect initiation of the first technology activity event bya user at the respective application (201 a, 201 b, 201 c). In responseto determining that the first technology activity event matches theproactively predicted technology activity event, the proactive processor(214 a-214 c) may then initiate the first technology activity eventusing the first adapted hierarchical cache data object. Because only therelevant or required cache data objects of the plurality of adaptedhierarchical cache data objects 340 are fetched, the network bandwidthusage is minimal and not cluttered, and the activity processing time isreduced because the required cached data is already fetched andavailable before the processing of the activity has even begun.

FIG. 3A depicts a high level process flow 300A for dynamic management ofstored cache data by construction of adapted hierarchical cache dataobjects, in accordance with one embodiment of the present invention.FIG. 3B depicts a schematic representation 300B of cached data inaccordance with conventional system. FIG. 3C depicts a schematicrepresentation 3000 of adapted hierarchical cache data objects, inaccordance with one embodiment of the present invention. In someembodiments, the processing device 138 of the caching technology system106 may execute the computer-readable program code/instructions 142 toperform one or more steps of the process flow 300A. The cachingtechnology system 106 may perform some or all of the steps of theprocess flow 300A, or cause other devices (entity system 180, entitydatabase 190, and/or other devices communicating via network 101) toperform some or all of the steps of the process flow 300A. The processflow 300A is structured for dynamic management of stored cache data.Here, the process flow 300A is directed to light-weight granular datacaching based on construction of adapted hierarchical data objects withimproved indexing, for reducing memory and processing burdens on datacaching servers and reducing turnaround time for activity execution.

As discussed previously, conventional systems store cached data inimmense files. As a non-limiting schematic depiction of conventionalcached data 312, FIG. 3B illustrates the cached data 314 a associatedwith user 1 and cached data 418 a associated with user N, where thecached data contents 316 a-316 n and 320 a-320 n, respectively, arestructured on an immense amalgamated indivisible manner, with a verylarge file size. Moreover, the expiration time (314 b, 318 b), if any atall, is assigned for the entirety of the cached data 314 a associatedwith user 1 and cached data 418 a associated with user N, and istypically a constant duration.

Now referring to FIGS. 3A and 3C, initially, at block 302, the systemmay initiate, via a proactive processor application (214 a-214 c), atechnology usage analysis mechanism comprising technology usage dataassociated with a plurality of users. In some embodiments, initiatingthe technology usage analysis mechanism further comprises retrieving,via a usage monitor engine application, metadata associated with priortechnology usage events associated with the plurality of users, whereinthe prior technology usage events comprise a user activity logassociated with activities initiated by the plurality of users using oneor more network devices associated with one or more communicationchannels. As a part of the technology usage analysis mechanism, theentity layer 204 may transmit an event feed comprising technology usagedata (e.g., metadata associated with the initiated activities,activities being processed, completed activities, and/or the like)tagged against a user specific access to the usage monitor engine 220.In some embodiments, the entity layer 204 may cross-tag the metadatawith respective activity attributes such as (i) activity channelattributes (e.g., type of communication channel, associated technologyapplication, etc.), (ii) activity parameters (e.g., activity type,authentication requirements, activity time interval, activity duration,etc.), (iii) data required for processing of the activity (e.g., cacheddata fetched, data transmitted, etc.), and/or the like, for eachindividual user. The usage monitor engine 220 is structured to analyzeevent metadata retrieved from the entity layer 204 (and/or the proactiveprocessors 214 a-214 c,) over time to determine/construct usage patternsfor each user, and for each specific channel that the user utilizes forconducting network activity events. The usage monitor engine 220 isstructured to analyze event metadata retrieved from the entity layer 204and/or the proactive processors 214 a-214 c, over time todetermine/construct usage patterns for each user, and for each specificchannel that the user utilizes for conducting network activity events.As a non-limiting example, the system (e.g., via the usage monitorengine 220) may determine that a first user typically performs task typeA (e.g., viewing a particular user information interface of a technologyapplication) using a communications channel and associated technologyapplication type B about every month, while another second usertypically performs the same task type A (e.g., viewing a particular userinformation interface of a technology application) using acommunications channel and associated technology application type Cdaily, and hence the required data needs to be cached with differenttime to live parameters and in different compatible formats (e.g.,objects may be fetched proactively based on prior frequency of use).

The system may then construct, via the proactive processor application(214 a-214 c), an adapted truncated cache data retrieval command suchthat the truncated cache data retrieval command is structured toselectively retrieve data that matches the technology usage data, andnot retrieve data that is not pertinent to the technology usage data. Insome embodiments, constructing the adapted truncated cache dataretrieval command further comprises analyzing the metadata associatedwith the prior technology usage events associated with the plurality ofusers; constructing, for each of the plurality of users, at least oneuser access routine based on determining one or more usage patterns inthe metadata associated with the prior technology usage events, whereindetermining one or more usage patterns further comprises determining amatch between metadata associated with a first prior technology usageevent at a first time interval, and metadata associated with a priorsecond technology usage event at a second time interval succeeding thefirst time interval, wherein the at least one user access routinecomprises one or more user activity events based on the one user accessroutine; determining, for each of the plurality of users, (i) one ormore event attributes associated with each of the one or more useractivity events in the associated at least one user access routine, and(ii) compatible cache data objects associated with the one or more eventattributes; and constructing, for each of the plurality of users, theadapted truncated cache data retrieval command to retrieve thecompatible cache data objects associated with the one or more eventattributes associated with the at least one user access routine. Here,determining one or more usage patterns may further comprise determininga match between metadata associated with a first sequence of priortechnology usage events at a third time interval, and metadataassociated with a second sequence of prior technology usages event at afourth time interval succeeding the third time interval.

At block 304, the system may trigger, via the proactive processor (214a-214 c), retrieval of truncated technology data for caching from ausage database 270 based on the adapted truncated cache data retrievalcommand. The system (e.g., at the proactive processors 214 a-214 c) mayanalyze the determined usage patterns, and determines the specifictechnology data to be cached for likely recurring events and thecompatible format and data transformation required for the respectivechannel of the predicted event. The system (e.g., at the proactiveprocessors 214 a-214 c) may trigger retrieval of truncated technologydata (i.e., only the specific data portions that are required to becached) for caching from a usage database (SOR event datahub 270), e.g.,via entity layer 204 in communication with applicable the service layercomponents such as entity service data type 1 205 a (e.g., rewards datatype), entity service data type 2 205 b (e.g., user information datatype), and entity service data type 3 205 c (e.g., bookings data type).

Next, at block 306, the system may construct a plurality of adaptedhierarchical cache data objects 340, for each of the plurality of users,in a distributed cache layer. Here, as illustrated by FIG. 3C, thesystem may identify a plurality of data element types 344 in theretrieved truncated technology data based on parsing the retrievedtruncated technology data. Then, for each of the plurality of dataelement types 344, the system may split the retrieved truncatedtechnology data into a plurality of cache data objects 346 such thateach of the plurality of cache data objects 340 comprises an associateddata element type 344. The system may further determine a hierarchy ofeach of the plurality of cache data objects, such as whether the cachedata object 346 is a standalone data type for use in a particularactivity, whether the cache data object 346 is to be accompanied by aparent data object or another object pair, that would need to be usedtogether in the particular activity, and/or the like. The system maythen transform the plurality of cache data objects into the plurality ofadapted hierarchical cache data objects 340 based on the determinedhierarchy, wherein each of the adapted hierarchical cache data objectsare (i) mapped to an associated cache data object identifier (DS1, DS2,. . . , DSN etc.), and (ii) linked to a parent user identifier dataelement 342. The parent user identifier data element 342 may beassociated with a unique identifier for each of the adapted hierarchicalcache data objects, which may also be structured to indicate theassociated user, any linked objects, hierarchy and/or the like.

As non-limiting examples, as illustrated by FIG. 3C, the system mayconstruct a first cache data object 340 a for a first user, associatedwith a user identifier data element 1 342 a having content cache dataobject 1 346 a of a data element type 1 344 a (e.g., user information).The system may construct a second cache data object 340 b for the firstuser, associated with the user identifier data element 1 342 a havingcontent cache data object 1 346 b of a data element type 2 344 b (e.g.,booking details). The first cache data object 340 a and the second cachedata object 340 b may be mapped together by link DS1. The system mayconstruct a third cache data object 340 c for the first user, associatedwith the user identifier data element 1 342 a having content cache dataobject 1 346 c of a data element type 3 344 c. The first cache dataobject 340 a and the third cache data object 340 c may be mappedtogether by link DS2. The system may construct a standalone first cachedata object 340 d for a second user, associated with a user identifierdata element 2 342 b having content cache data object 1 346 d of a dataelement type 1 344 d. The system may construct a second cache dataobject 340 e for the second user, associated with the user identifierdata element 2 342 b having content cache data object 1 346 e of a dataelement type 1 344 e. The second cache data object 340 e for the seconduser and another associated third cache data object 340 f for the seconduser may be mapped together by link DSN. The system may construct a Nthcache data object 340 n for an Nth user, associated with the useridentifier data element N 342 n having cache data content of cache dataobject 1 346 f of a data element type 1 344 f. In this manner, asindicated by block 308, the system may cache the constructed pluralityof adapted hierarchical cache data objects 340, for each of theplurality of users, in the distributed cache layer 260.

Next, at block 310, the system may, for each of the plurality of adaptedhierarchical cache data objects of each of the plurality of users,determine an associated determine a time to live parameter 352. Here,the system may link the determined time to live parameter 352 to theassociated adapted hierarchical cache data object such that the adaptedhierarchical cache data object is (i) stored only for a first timeinterval associated with the duration of the time to live parameter 352,and (ii) dynamically expunged upon elapse of the first time intervalassociated with the time to live parameter 352. The system determinesindividual specific time to live parameters for each of the objects 340that is particular to the data element type, the frequency of use, typeof communication channel, usage patterns of the user, and/or the like,that pertain to the specific object 340. Continuing with thenon-limiting examples of FIG. 3C, the system may determine a time tolive parameter 1 352 a of duration 1 (e.g., 1 hour) for the first cachedata object 340 a for the first user, a time to live parameter 1 352 bof another duration 2 (different from duration 1) for the second cachedata object 340 a for the first user, a time to live parameter 1 352 cof another duration 3 (e.g., 6 hours) for the third cache data object340 c for the first user, a time to live parameter 1 352 d of anotherduration 4 (e.g., 12 hours) for the first cache data object 340 d forthe second user, a time to live parameter 1 352 e of duration 1 (e.g., 1hour) for the second cache data object 340 e for the second user, and atime to live parameter 1 352 f of another duration 5 for the Nth cachedata object 340 n for the Nth user.

The determined time to live parameter 352 relates to how long the cacheddata is stored before it is discarded. Moreover, the time to liveparameter 352 is customized and tailored to the specific user and thespecific activity. For example, the time to live parameter may bedetermined to be 3 hours for a second technology activity event, and 40minutes for a third technology activity event, based on analyzing theprior activity event data and data associated with the particularinterdependent technology activity event (e.g., time duration forprocessing the activity event). The cached data may be erased from thecached data storage (e.g., 212 a, 212 b, 212 c) upon elapse of the timeto live parameters, e.g., irrespective of whether the data has beenutilized for performing the interdependent technology activity events,thereby preventing undesirable burdens on cache memory devices due toperpetual or long-term storage of likely unnecessary cached data. Thetime to live parameter may be determined using a function that processesvariables such as a context severity (e.g., intent severity), useractivity information/data, and/or the like. In some embodiments, thecontext severity may refer to a probability score of the interdependenttechnology activity event occurring, prior repetitions/reoccurrences ofuser activities, and/or the like.

As discussed above, different hierarchical cache data objects 340 of thesame user may comprise differing time to live parameters. In someembodiments, the plurality of adapted hierarchical cache data objects340 associated with a first user comprise a first adapted hierarchicalcache data object (e.g., object 340 a) and a second adapted hierarchicalcache data object of the plurality of adapted hierarchical cache dataobjects 340 (e.g., object 340 b). Here, determining the associated timeto live parameter 352 further comprises determining a first time to liveparameter 352 (e.g., 1 hour) associated with the first adaptedhierarchical cache data object of the first user, and determining asecond time to live parameter 352 (e.g., 35 minutes) associated with thesecond adapted hierarchical cache data object of the first user. Here,the first time to live parameter 352 exceeds the second time to liveparameter 352 such that the second adapted hierarchical cache dataobject is dynamically expunged prior to the dynamic expunging of thefirst adapted hierarchical cache data object.

As discussed above, hierarchical cache data objects 340 of differentusers, eve of the same type or being substantially similar, user maycomprise differing time to live parameters based on the usage patternsof each particular user. In some embodiments, the plurality of adaptedhierarchical cache data objects 340 comprise a first adaptedhierarchical cache data object associated with a first user, and asecond adapted hierarchical cache data object associated with a seconduser, wherein the first adapted hierarchical cache data object matchesthe second adapted hierarchical cache data object. Here, determining theassociated time to live parameter 352 further comprises: determining afirst time to live parameter 352 associated with the first adaptedhierarchical cache data object of the first user; and determining asecond time to live parameter 352 associated with the second adaptedhierarchical cache data object of the second user; and wherein the firsttime to live parameter 352 exceeds the second time to live parameter 352such that the second adapted hierarchical cache data object isdynamically expunged prior to the dynamic expunging of the first adaptedhierarchical cache data object.

Moreover, the time to live parameters may be determined for each of thestorage locations of the particular adapted hierarchical cache dataobject. For instance, the same object may be stored at a shorter timewhen stored at cache locations 212 a-212 c, than when stored at othercache locations such as the entity layer 204, or at the distributedcache 240. In some embodiments, determining the associated time to liveparameter 352 further comprises, for a first adapted hierarchical cachedata object of the plurality of adapted hierarchical cache data objects340 of a first user of the plurality of users, determining an associatedfirst storage level location and a second storage level location.Moreover, the system may determine a first time to live parameter 352associated with the first storage level location, and determining asecond time to live parameter 352 associated with the second storagelevel location, wherein the first time to live parameter 352 exceeds thesecond time to live parameter 352 such that the first adaptedhierarchical cache data object at the second storage level location isdynamically expunged prior to the dynamic expunging of the first adaptedhierarchical cache data object at the first storage level location.

In some embodiments, the system may detect, via a proactive processorapplication (214 a-214 c), a first access event via a first networkdevice associated with a first communication channel at a first timeinterval, such that the first access event is detected prior toinitiation of a first technology activity event by the user. The systemmay then populate a first adapted hierarchical cache data object of theconstructed plurality of adapted hierarchical cache data objects 340 foruse at a technology application associated with the first network deviceprior to the initiation of the first technology activity event by theuser, as will be described in detail with respect to FIG. 4 later on.

In some embodiments, the system may construct one or more additionalchild cache data objects, and append the plurality of adaptedhierarchical cache data objects 340 with the one or more additionalchild cache data objects.

In some embodiments, the system may determine an update to a system ofrecords database system, and expunge the plurality of adaptedhierarchical cache data objects 340 in real-time, in response todetermining the update to a system of records database system. Moreover,the system transmits control signals to the application layer 201 tocause the application layer 201 and/or its relevant components (e.g.,via relevant proactive processors 214 a-214 c) to perform periodic scansof storage locations or systems where user data or activity data isstored, such as the entity database 190, record (SOR) event data hub270, the service layer 205, etc., to check for recent updates to thedata and to determine data that is rendered incompatible and/orredundant in light of the recent updates, to determine obsolete cacheddata, and/or the like. Consequently, the system transmits controlsignals to the cache layer (e.g., associated with distributed cachedatabase 260 of FIG. 2B), to cause it to (i) flush incompatible,redundant and obsolete data, and (ii) update relevant cache data objectsaccordingly (e.g., by only constructing new cache data objects for thespecific fragments of updated data). In this regard, specifically, thesystem is structured to map adapted hierarchical cache data objects 340to database storage columns (e.g., that of the entity database 190,record (SOR) event data hub 270, the service layer 205, etc.). Here, thecache layer flushes the incompatible, redundant and obsolete storedthereon by integrating the determined recent updates (and the determinedincompatible, redundant and obsolete data) with the mapping of theadapted hierarchical cache data objects 340 to database storage columns.As an improvement provided by the present invention, the cache layer mayselectively flush only relevant fragments of cached data, i.e., onlyrelevant (to the determined updates) adapted hierarchical cache dataobjects of the plurality of the adapted hierarchical cache data objects340, instead of undesirably flushing all of the cached data, or none ofthe cached data. Conventional systems store cached data in immensefiles, and are not capable of selectively flushing or updating specificfragments of data within the immense stored data. In this manner, thepresent invention keeps the cache layer lighter by removingincompatible, redundant and obsolete data objects and improves indexingon the cache layer.

In some embodiments, the system may, for each of the plurality ofadapted hierarchical cache data objects 340 of each of the plurality ofusers, determine an associated determine a time to fetch parameter; andlink the determined time to fetch parameter to the associated adaptedhierarchical cache data object. In some embodiments, the system may, foreach of the plurality of adapted hierarchical cache data objects 340 ofeach of the plurality of users, dynamically update the adaptedhierarchical cache data object at a time interval preceding theassociated determined time to fetch parameter. The time to fetchparameter may refer to the optimal time for fetching the requiredadapted hierarchical cache data objects for a likely technology activityevent to be initiated by the user, without the data becoming obsolete bythe time the technology activity event is performed. In other words, thetime to fetch parameter indicates how long before the technologyactivity event does the required adapted hierarchical cache data objectsneed to be fetched, such that the most current data is available at thetime of performing the technology activity event, without the databecoming obsolete by the time the technology activity event isperformed. The time to fetch parameters are structured to precluderequired adapted hierarchical cache data objects from being fetched atstored at the cache storage locations 212 a-212 c too far in advance ofthe technology activity event, thereby ensuring that cache storagelocations 212 a-212 c are not overloaded with large amounts of data forprolonged time periods, and ensuring that the most current data isavailable at the time of performing the technology activity event. Therequired adapted hierarchical cache data objects that are fetched toofar in advance of the technology activity event may undesirably becomeobsolete or irrelevant and thereby be unusable or cause errors inperforming the subsequent technology activity event.

FIG. 4 depicts a high level process flow 400 for dynamic management ofstored cache data, in accordance with one embodiments of the presentinvention. In some embodiments, the processing device 138 of the cachingtechnology system 106 may execute the computer-readable programcode/instructions 142 to perform one or more steps of the process flow400. The caching technology system 106 may perform some or all of thesteps of the process flow 400, or cause other devices (entity system180, entity database 190, and/or other devices communicating via network101) to perform some or all of the steps of the process flow 400. Theprocess flow 400 is structured for dynamic management of stored cachedata. Here, the process flow 400 is structured for proactive alleviationof obsolete data, dynamic pre-population and fetching of cached databased on determining actions preceding initiation of activities, forpreventing data redundancy based errors, and for reducing memory andprocessing burdens on data caching servers and reducing turnaround timefor activity execution.

Initially, at block 402, the system may detect, via a proactiveprocessor application (214 a-214 c), a first access event via a firstnetwork device associated with a first communication channel at a firsttime interval. Here, the first access event (e.g., detecting the userhas opened a particular application, the user is in the process ofinputting login credentials, etc.) is detected prior to initiation of afirst technology activity event by the user. The first networked devicemay be a user device 104, a user auxiliary device 170, a resourceprocessing device 120, and/or the like.

Next, the system may, determine a proactive technology activity eventassociated with the user that is (i) compatible with the first networkdevice associated with a first communication channel and (ii) matchesthe first access event. Here, the system may determine access attributesand metadata associated with the first access event. The system may thenretrieve, via the usage monitor engine application 220, metadataassociated with prior technology usage events associated with the users.The system may then determine a first user access routine based ondetermining one or more usage patterns in the metadata associated withthe prior technology usage events that match the access attributesassociated with the first access event. The system may then determine aproactive technology activity event associated with the user that is (i)compatible with the first network device associated with a firstcommunication channel and (ii) matches the first user access routine.Here, the proactive processors 214 a-214 c may extract metadataassociated with access events associated with the respective coupledchannel (e.g., via communication channels 216 a, 216 b, 216 c), transmitthe extracted metadata to a usage monitor engine 220 for analyzing themetadata of the access event to determine a likely technology activityevent to be initiated by the user at the respective channel. Theproactive processor (214 a-214 c) may then analyze the predicted likelytechnology activity event to be initiated by the user at the respectivechannel, and further determine the data required and relevant for itsprocessing.

Next, the system may, determine a first adapted hierarchical cache dataobject 340 a of the plurality of adapted hierarchical cache data objects340 associated with the first user that is compatible with the proactivetechnology activity event. Here, the system may determine one or moreevent attributes associated with the proactive technology activityevent; and determine the first adapted hierarchical cache data object340 a of the plurality of adapted hierarchical cache data objects 340associated with the first user that is compatible with the one or moreevent attributes of the proactive technology activity event. Theproactive processor (214 a-214 c) may further determine that specificcache data objects associated with the required data.

Next, the system may, trigger one or more data presence checksassociated with the first adapted hierarchical cache data object 340 aat one or more technology network layers. In response to a successfuldata presence check, the system may selectively retrieve truncated cachedata that matches the proactive technology activity event. In someembodiments, selectively retrieving truncated cache data comprisesretrieving truncated cache data that matches one or more eventattributes of the proactive technology activity event, further comprisesretrieving the first adapted hierarchical cache data object 340 a of theplurality of adapted hierarchical cache data objects 340 associated withthe first user that is compatible with the one or more event attributesof the proactive technology activity event. Here, the proactiveprocessor (214 a-214 c) may trigger the entity layer 204 (e.g., viarespective communication channels 218 a, 218 b, 218 c) to check if therelevant and required (for the determined likely activity to beinitiated by the user) adapted hierarchical cache data objects arepresent at the entity layer 204, and in not, fetch the same from thedistributed cache 260 at the cache layer to the entity layer 204 (viacommunication channel 262). The extracted relevant and required (for thedetermined likely activity to be initiated by the user) adaptedhierarchical cache data objects of the plurality of the adaptedhierarchical cache data objects 340 may then be populated at therespective cache data stores (212 a, 212 b, 212 c) via the proactiveprocessor (214 a-214 c).

In some embodiments, the system may trigger a first data presence checkassociated with the first adapted hierarchical cache data object 340 aat an application layer associated with the first communication channel(e.g., at cache stores 212 a-212 c). In response to a successful firstdata presence check, the system may selectively retrieve truncated cachedata that matches the one or more event attributes of the proactivetechnology activity event, comprising selectively retrieving the firstadapted hierarchical cache data object 340 a of the plurality of adaptedhierarchical cache data objects 340 associated with the first user thatis compatible with the one or more event attributes of the proactivetechnology activity event at a second time interval prior to initiationof the first technology activity event by the user.

In response to an unsuccessful first data presence check, the system maytrigger a second data presence check associated with the first adaptedhierarchical cache data object 340 a at an entity layer associated withthe first communication channel. In response to a successful second datapresence check, the system may selectively retrieve truncated cache datathat matches the one or more event attributes of the proactivetechnology activity event, comprising: retrieving the first adaptedhierarchical cache data object 340 a of the plurality of adaptedhierarchical cache data objects 340 associated with the first user thatis compatible with the one or more event attributes of the proactivetechnology activity event prior to initiation of the first technologyactivity event by the user; and transmitting retrieved the first adaptedhierarchical cache data object 340 a from the entity layer to theapplication layer prior to initiation of the first technology activityevent by the user.

In some embodiments, selectively retrieving truncated cache data,further comprises accessing the plurality of adapted hierarchical cachedata objects 340 associated with a plurality of users, and indexing theplurality of adapted hierarchical cache data objects 340 associated witha plurality of users based on a parent user identifier data elementassociated with the first user. The adapted hierarchical cache dataobjects 340 may be indexed based on the user identifier data elements342.

Next, at block 404, the system may populate the first adaptedhierarchical cache data object 340 a for use at a technology applicationassociated with the first network device prior to the initiation of thefirst technology activity event by the user. Here, the system maydetermine a time latency associated with the proactive technologyactivity event, wherein determining the time latency comprisesdetermining a time to fetch parameter associated with the first adaptedhierarchical cache data object; proactively extract, via a data cachingapplication, the first adapted hierarchical cache data object 340 a at apredetermined first time interval preceding a second time associatedwith initiation of the second technology activity event, wherein thepredetermined first time interval is associated with the determined timeto fetch parameter associated with the time latency of the firsttechnology activity event.

The system may detect initiation of the first technology activity eventby a user at a second time interval via the first network deviceassociated with the first communication channel, as indicated by block406. Subsequently, the proactive processor (214 a-214 c) may detectinitiation of the first technology activity event by a user at therespective application (201 a, 201 b, 201 c). In response to determiningthat the first technology activity event matches the proactivelypredicted technology activity event, the proactive processor (214 a-214c) may then initiate the first technology activity event using the firstadapted hierarchical cache data object. Because only the relevant orrequired cache data objects of the plurality of adapted hierarchicalcache data objects 340 are fetched, the network bandwidth usage isminimal and not cluttered, and the activity processing time is reducedbecause the required cached data is already fetched and available beforethe processing of the activity has even begun.

Next at block 408, the system may, in response to determining that thefirst technology activity event matches the proactive technologyactivity event, initiate the first technology activity event using thefirst adapted hierarchical cache data object. Here, the system mayprocess the first technology activity event, and upon completion presenta user interface indicating completion or status of the first technologyactivity event.

In some embodiments, the system may determine an update to a system ofrecords database system; and expunge the plurality of adaptedhierarchical cache data objects 340 in real-time, in response todetermining the update to a system of records database system. Moreover,the system transmits control signals to the application layer 201 tocause the application layer 201 and/or its relevant components (e.g.,via relevant proactive processors 214 a-214 c) to perform periodic scansof storage locations or systems where user data or activity data isstored, such as the entity database 190, record (SOR) event data hub270, the service layer 205, etc., to check for recent updates to thedata and to determine data that is rendered incompatible and/orredundant in light of the recent updates, to determine obsolete cacheddata, and/or the like. Consequently, the system transmits controlsignals to the cache layer (e.g., associated with distributed cachedatabase 260 of FIG. 2B), to cause it to (i) flush incompatible,redundant and obsolete data, and (ii) update relevant cache data objectsaccordingly (e.g., by only constructing new cache data objects for thespecific fragments of updated data). In this regard, specifically, thesystem is structured to map adapted hierarchical cache data objects 340to database storage columns (e.g., that of the entity database 190,record (SOR) event data hub 270, the service layer 205, etc.). Here, thecache layer flushes the incompatible, redundant and obsolete storedthereon by integrating the determined recent updates (and the determinedincompatible, redundant and obsolete data) with the mapping of theadapted hierarchical cache data objects 340 to database storage columns.As an improvement provided by the present invention, the cache layer mayselectively flush only relevant fragments of cached data, i.e., onlyrelevant (to the determined updates) adapted hierarchical cache dataobjects of the plurality of the adapted hierarchical cache data objects340, instead of undesirably flushing all of the cached data, or none ofthe cached data. Conventional systems store cached data in immensefiles, and are not capable of selectively flushing or updating specificfragments of data within the immense stored data. In this manner, thepresent invention keeps the cache layer lighter by removingincompatible, redundant and obsolete data objects and improves indexingon the cache layer. In some embodiments, the system may for each of theplurality of adapted hierarchical cache data objects 340 of each of theplurality of users, dynamically update the adapted hierarchical cachedata object at a time interval preceding the associated determined timeto fetch parameter.

As will be appreciated by one of ordinary skill in the art, the presentinvention may be embodied as an apparatus (including, for example, asystem, a machine, a device, a computer program product, and/or thelike), as a method (including, for example, a business process, acomputer-implemented process, and/or the like), or as any combination ofthe foregoing. Accordingly, embodiments of the present invention maytake the form of an entirely software embodiment (including firmware,resident software, micro-code, and the like), an entirely hardwareembodiment, or an embodiment combining software and hardware aspectsthat may generally be referred to herein as a “system.” Furthermore,embodiments of the present invention may take the form of a computerprogram product that includes a computer-readable storage medium havingcomputer-executable program code portions stored therein. As usedherein, a processor may be “configured to” perform a certain function ina variety of ways, including, for example, by having one or morespecial-purpose circuits perform the functions by executing one or morecomputer-executable program code portions embodied in acomputer-readable medium, and/or having one or more application-specificcircuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, infrared, electromagnetic, and/orsemiconductor system, apparatus, and/or device. For example, in someembodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as apropagation signal including computer-executable program code portionsembodied therein.

It will also be understood that one or more computer-executable programcode portions for carrying out the specialized operations of the presentinvention may be required on the specialized computer includeobject-oriented, scripted, and/or unscripted programming languages, suchas, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, ObjectiveC, and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

It will further be understood that some embodiments of the presentinvention are described herein with reference to flowchart illustrationsand/or block diagrams of systems, methods, and/or computer programproducts. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions.

It will also be understood that the one or more computer-executableprogram code portions may be stored in a transitory or non-transitorycomputer-readable medium (e.g., a memory, and the like) that can directa computer and/or other programmable data processing apparatus tofunction in a particular manner, such that the computer-executableprogram code portions stored in the computer-readable medium produce anarticle of manufacture, including instruction mechanisms which implementthe steps and/or functions specified in the flowchart(s) and/or blockdiagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with operator and/orhuman-implemented steps in order to carry out an embodiment of thepresent invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

To supplement the present disclosure, this application furtherincorporates entirely by reference the following commonly assignedpatent application:

U.S. Patent Application Docket Number Ser. No. Title Filed On13121US1.014033.4337 To be assigned SYSTEMS AND METHODS Concurrently FORDYNAMIC herewith MANAGEMENT OF STORED CACHE DATA BASED ON USAGEINFORMATION

1. A system for dynamic management of stored cache data based onpredictive usage information, wherein the system is structured forproactive alleviation of obsolete data, dynamic pre-population andfetching of cached data based on determining actions precedinginitiation of activities, for preventing data redundancy based errors,and reducing memory and processing burdens on data caching servers andreducing turnaround time for activity execution, the system comprising:at least one memory device with computer-readable program code storedthereon; at least one communication device; at least one processingdevice operatively coupled to the at least one memory device and the atleast one communication device, wherein executing the computer-readableprogram code is configured to cause the at least one processing deviceto: detect, via a proactive processor application, a first access eventvia a first network device associated with a first communication channelat a first time interval, such that the first access event is detectedprior to initiation of a first technology activity event by a firstuser; determine a proactive technology activity event associated withthe first user that is (i) compatible with the first network deviceassociated with the first communication channel and (ii) matches thefirst access event; determine a first adapted hierarchical cache dataobject of a plurality of adapted hierarchical cache data objectsassociated with the first user that is compatible with the proactivetechnology activity event; trigger one or more data presence checksassociated with the first adapted hierarchical cache data object at oneor more technology network layers; in response to a successful datapresence check, selectively retrieve truncated cache data that matchesthe proactive technology activity event; populate the first adaptedhierarchical cache data object for use at a technology applicationassociated with the first network device prior to the initiation of thefirst technology activity event by the first user; detect initiation ofthe first technology activity event by the first user at a second timeinterval via the first network device associated with the firstcommunication channel; and in response to determining that the firsttechnology activity event matches the proactive technology activityevent, initiate the first technology activity event using the firstadapted hierarchical cache data object.
 2. The system of claim 1,wherein determining proactive technology activity event associated withthe first user further comprises: determine access attributes associatedwith the first access event; retrieve, via a usage monitor engineapplication, metadata associated with prior technology usage eventsassociated with the first user; determine a first user access routinebased on determining one or more usage patterns in the metadataassociated with the prior technology usage events that match the accessattributes associated with the first access event; and determine aproactive technology activity event associated with the first user thatis (i) compatible with the first network device associated with thefirst communication channel and (ii) matches the first user accessroutine.
 3. The system of claim 1, wherein determining the first adaptedhierarchical cache data object of the plurality of adapted hierarchicalcache data objects further comprises: determine one or more eventattributes associated with the proactive technology activity event; anddetermine the first adapted hierarchical cache data object of theplurality of adapted hierarchical cache data objects associated with thefirst user such that the first adapted hierarchical cache data object iscompatible with the one or more event attributes of the proactivetechnology activity event.
 4. The system of claim 1, wherein selectivelyretrieving truncated cache data comprises retrieving truncated cachedata that matches one or more event attributes of the proactivetechnology activity event, further comprising: retrieving the firstadapted hierarchical cache data object of the plurality of adaptedhierarchical cache data objects associated with the first user that iscompatible with the one or more event attributes of the proactivetechnology activity event.
 5. The system of claim 1, wherein executingthe computer-readable program code is configured to cause the at leastone processing device to: trigger a first data presence check associatedwith the first adapted hierarchical cache data object at an applicationlayer associated with the first communication channel.
 6. The system ofclaim 5, wherein executing the computer-readable program code isconfigured to cause the at least one processing device to: in responseto a successful first data presence check, selectively retrievetruncated cache data that matches one or more event attributes of theproactive technology activity event, comprising selectively retrievingthe first adapted hierarchical cache data object of the plurality ofadapted hierarchical cache data objects associated with the first usersuch that the first adapted hierarchical cache data object is compatiblewith the one or more event attributes of the proactive technologyactivity event at a second time interval prior to initiation of thefirst technology activity event by the first user.
 7. The system ofclaim 5, wherein executing the computer-readable program code isconfigured to cause the at least one processing device to: in responseto an unsuccessful first data presence check, trigger a second datapresence check associated with the first adapted hierarchical cache dataobject at an entity layer associated with the first communicationchannel.
 8. The system of claim 7, wherein executing thecomputer-readable program code is configured to cause the at least oneprocessing device to: in response to a successful second data presencecheck, selectively retrieve truncated cache data that matches one ormore event attributes of the proactive technology activity event,comprising: retrieving the first adapted hierarchical cache data objectof the plurality of adapted hierarchical cache data objects associatedwith the first user that is compatible with the one or more eventattributes of the proactive technology activity event prior toinitiation of the first technology activity event by the first user; andtransmitting the retrieved first adapted hierarchical cache data objectfrom the entity layer to the application layer prior to initiation ofthe first technology activity event by the first user.
 9. The system ofclaim 1, wherein selectively retrieving truncated cache data, furthercomprises: accessing the plurality of adapted hierarchical cache dataobjects associated with a plurality of users; and indexing the pluralityof adapted hierarchical cache data objects associated with the pluralityof users based on a parent user identifier data element associated withthe first user.
 10. The system of claim 1, wherein populate the firstadapted hierarchical cache data object for use at a technologyapplication associated with the first network device prior to theinitiation of the first technology activity event by the first user,further comprises: determine a time latency associated with theproactive technology activity event, wherein determining the timelatency comprises determining a time to fetch parameter associated withthe first adapted hierarchical cache data object; proactively extract,via a data caching application, the first adapted hierarchical cachedata object at a predetermined first time interval preceding a secondtime associated with initiation of a second technology activity event,wherein the predetermined first time interval is associated with thedetermined time to fetch parameter associated with the time latency ofthe first technology activity event.
 11. The system of claim 1, whereinexecuting the computer-readable program code is further configured tocause the at least one processing device to: determine an update to asystem of records database system; and expunge the plurality of adaptedhierarchical cache data objects in real-time, in response to determiningthe update to the system of records database system.
 12. The system ofclaim 1, wherein executing the computer-readable program code is furtherconfigured to cause the at least one processing device to: for each of aplurality of adapted hierarchical cache data objects of each of aplurality of users, dynamically update the adapted hierarchical cachedata object at a time interval preceding an associated determined timeto fetch parameter.
 13. A computer program product for dynamicmanagement of stored cache data based on predictive usage information,wherein the computer program product is structured for proactivealleviation of obsolete data, dynamic pre-population and fetching ofcached data based on determining actions preceding initiation ofactivities, for preventing data redundancy based errors, and reducingmemory and processing burdens on data caching servers and reducingturnaround time for activity execution, the computer program productcomprising a non-transitory computer-readable storage medium havingcomputer-executable instructions to: detect, via a proactive processorapplication, a first access event via a first network device associatedwith a first communication channel at a first time interval, such thatthe first access event is detected prior to initiation of a firsttechnology activity event by a first user; determine a proactivetechnology activity event associated with the first user that is (i)compatible with the first network device associated with the firstcommunication channel and (ii) matches the first access event; determinea first adapted hierarchical cache data object of a plurality of adaptedhierarchical cache data objects associated with the first user that iscompatible with the proactive technology activity event; trigger one ormore data presence checks associated with the first adapted hierarchicalcache data object at one or more technology network layers; in responseto a successful data presence check, selectively retrieve truncatedcache data that matches the proactive technology activity event;populate the first adapted hierarchical cache data object for use at atechnology application associated with the first network device prior tothe initiation of the first technology activity event by the first user;detect initiation of the first technology activity event by the firstuser at a second time interval via the first network device associatedwith the first communication channel; and in response to determiningthat the first technology activity event matches the proactivetechnology activity event, initiate the first technology activity eventusing the first adapted hierarchical cache data object.
 14. The computerprogram product of claim 13, wherein determining proactive technologyactivity event associated with the first user further comprises:determine access attributes associated with the first access event;retrieve, via a usage monitor engine application, metadata associatedwith prior technology usage events associated with the first user;determine a first user access routine based on determining one or moreusage patterns in the metadata associated with the prior technologyusage events that match the access attributes associated with the firstaccess event; and determine a proactive technology activity eventassociated with the first user that is (i) compatible with the firstnetwork device associated with the first communication channel and (ii)matches the first user access routine.
 15. The computer program productof claim 13, wherein determining the first adapted hierarchical cachedata object of the plurality of adapted hierarchical cache data objectsfurther comprises: determine one or more event attributes associatedwith the proactive technology activity event; and determine the firstadapted hierarchical cache data object of the plurality of adaptedhierarchical cache data objects associated with the first user such thatthe first adapted hierarchical cache data object is compatible with theone or more event attributes of the proactive technology activity event.16. The computer program product of claim 13, wherein the non-transitorycomputer-readable storage medium further comprises computer-executableinstructions to: trigger a first data presence check associated with thefirst adapted hierarchical cache data object at an application layerassociated with the first communication channel; and in response to asuccessful first data presence check, selectively retrieve truncatedcache data that matches one or more event attributes of the proactivetechnology activity event, comprising selectively retrieving the firstadapted hierarchical cache data object of the plurality of adaptedhierarchical cache data objects associated with the first user such thatthe first adapted hierarchical cache data object is compatible with theone or more event attributes associated with the proactive technologyactivity event at a second time interval prior to initiation of thefirst technology activity event by the first user.
 17. A method dynamicmanagement of stored cache data based on predictive usage information,wherein the method is structured for proactive alleviation of obsoletedata, dynamic pre-population and fetching of cached data based ondetermining actions preceding initiation of activities, for preventingdata redundancy based errors, and reducing memory and processing burdenson data caching servers and reducing turnaround time for activityexecution, the method comprising: detecting, via a proactive processorapplication, a first access event via a first network device associatedwith a first communication channel at a first time interval, such thatthe first access event is detected prior to initiation of a firsttechnology activity event by a first user; determining a proactivetechnology activity event associated with the first user that is (i)compatible with the first network device associated with the firstcommunication channel and (ii) matches the first access event;determining a first adapted hierarchical cache data object of aplurality of adapted hierarchical cache data objects associated with thefirst user that is compatible with the proactive technology activityevent; triggering one or more data presence checks associated with thefirst adapted hierarchical cache data object at one or more technologynetwork layers; in response to a successful data presence check,selectively retrieving truncated cache data that matches the proactivetechnology activity event; populating the first adapted hierarchicalcache data object for use at a technology application associated withthe first network device prior to the initiation of the first technologyactivity event by the first user; detecting initiation of the firsttechnology activity event by the first user at a second time intervalvia the first network device associated with the first communicationchannel; and in response to determining that the first technologyactivity event matches the proactive technology activity event,initiating the first technology activity event using the first adaptedhierarchical cache data object.
 18. The method of claim 17, whereindetermining proactive technology activity event associated with thefirst user further comprises: determine access attributes associatedwith the first access event; retrieve, via a usage monitor engineapplication, metadata associated with prior technology usage eventsassociated with the first user; determine a first user access routinebased on determining one or more usage patterns in the metadataassociated with the prior technology usage events that match the accessattributes associated with the first access event; and determine aproactive technology activity event associated with the first user thatis (i) compatible with the first network device associated with thefirst communication channel and (ii) matches the first user accessroutine.
 19. The method of claim 17, determining the first adaptedhierarchical cache data object of the plurality of adapted hierarchicalcache data objects further comprises: determine one or more eventattributes associated with the proactive technology activity event; anddetermine the first adapted hierarchical cache data object of theplurality of adapted hierarchical cache data objects associated with thefirst user such that the first adapted hierarchical cache data object iscompatible with the one or more event attributes of the proactivetechnology activity event.
 20. The method of claim 17, wherein themethod further comprises: triggering a first data presence checkassociated with the first adapted hierarchical cache data object at anapplication layer associated with the first communication channel; andin response to a successful first data presence check, selectivelyretrieving truncated cache data that matches one or more eventattributes of the proactive technology activity event, comprisingselectively retrieving the first adapted hierarchical cache data objectof the plurality of adapted hierarchical cache data objects associatedwith the first user such that the first adapted hierarchical cache dataobject is compatible with the one or more event attributes associatedwith the proactive technology activity event at a second time intervalprior to initiation of the first technology activity event by the firstuser.